Method and apparatus for facilitating device hibernation

ABSTRACT

One embodiment of the present invention provides a system that enables a computing device to save additional power by entering a “hibernation mode,” wherein the active state of the computing device is preserved in non-volatile storage while power to volatile storage is turned off. During operation, the system reanimates a computing device from a hibernation image by restoring reanimation code from the hibernation image and then executing the reanimation code. While executing this reanimation code, the system restores the rest of the hibernation image by, reading compressed data containing the rest of the hibernation image, and decompressing the compressed data using computational circuitry within the computing device. During this process, the decompression operations are overlapped with the reading operations to improve performance.

BACKGROUND

1. Field of the Invention

The present invention relates generally to techniques for saving powerin computing devices. More specifically, the present invention relatesto a method and an apparatus for facilitating device hibernation,wherein the active state of a computing device is preserved while powerto the computing device is turned off.

2. Related Art

Power conservation is critically important for many types of computersystems. For example, portable computer systems need to conserve powerin order to operate for long periods of time on battery power. Powerconservation is also important for desktop computer systems in order tomeet the strict power-usage requirements for ENERGY STAR qualification.

Many computer systems save power by entering a power-saving state knownas “sleep mode,” when they are not busy. During sleep mode, power issaved by placing much of the computer system in a low-power state, whilepower is maintained to volatile memory. Maintaining power to volatilememory preserves the active state of the computer system and therebyfacilitates a nearly instant wake-up process, which provides anexcellent user experience.

One drawback of existing sleep systems is that if power is lost duringsleep mode, any unsaved work in volatile memory disappears. This loss ofpower can be easily triggered if a user is distracted for a few hours,or takes too long when performing a sleep-swap of the system battery.Unfortunately, as computer systems begin to incorporate larger amountsof random-access memory (RAM), correspondingly more power is requiredkeep this RAM memory powered up during sleep mode. At the same time, asportable computer systems become progressively thinner and lighter, theycontain correspondingly smaller batteries.

As a consequence of these trends, a few years ago, a laptop computersystem could be expected to last multiple days in sleep mode, whereas atpresent, a new laptop computer system can rarely last more than a fullday in sleep mode when it is configured with a maximum amount of RAM.

Hence, what is needed is a method and an apparatus that enables computersystems to save additional power beyond what can be saved by enteringsleep mode.

SUMMARY

One embodiment of the present invention provides a system that enables acomputing device to save additional power by entering a “hibernationmode,” wherein the active state of the computing device is preserved innon-volatile storage while power to volatile storage is turned off.During operation, the system reanimates a computing device from ahibernation image by restoring reanimation code from the hibernationimage and then executing the reanimation code. While executing thisreanimation code, the system restores the rest of the hibernation imageby, reading compressed data containing the rest of the hibernationimage, and decompressing the compressed data using computationalcircuitry within the computing device. During this process, thedecompression operations are overlapped with the reading operations toimprove performance.

In a variation of this embodiment, restoring the rest of the hibernationimage involves reading a decryption key from non-volatile random accessmemory, and using the decryption key to decrypt portions of thecompressed data containing the rest of the hibernation image which wereencrypted prior to storage in non-volatile memory.

In a variation on this embodiment, prior to restoring the reanimationcode, the system compares a stored booter checksum, which was storedwhile generating the hibernation image, against a current booterchecksum for a booter which is currently restoring the animation code.If the stored booter checksum does not match the current booterchecksum, the system discontinues the reanimation process.

In a variation on this embodiment, prior to restoring the reanimationcode, the system examines stored device configuration information, whichwas stored when the hibernation image was generated, to determinewhether the configuration of the computing device has changed since thehibernation image was generated. If so, the system discontinues thereanimation process.

In a variation on this embodiment, after the hibernation image isdecompressed, the system performs a wake-from-sleep operation toreanimate the computing device from the decompressed hibernation image.

In a variation on this embodiment, the system additionally sets areanimation flag so that hibernation-aware drivers will know thewake-from-sleep operation is not a normal wake-from-sleep operation, butis instead part of a reanimation operation.

In a variation on this embodiment, prior to restoring the reanimationimage, the system creates the hibernation image. This involves: (1)reserving space for the hibernation image in non-volatile storage; (2)forming the hibernation image by compressing portions of the activestate of the computing device to form the compressed data and generatingthe reanimation code; and (3) storing the hibernation image innon-volatile storage.

In a further variation, creating the hibernation image additionallyinvolves: (1) encrypting portions of the hibernation image, and storinga corresponding decryption key; (2) storing a booter checksum for abooter which will restore the hibernation image; (3) setting and storinga hibernation flag which indicates that a hibernation image has beenstored; (4) storing a block number indicating where the hibernationimage is stored; and (5) storing system configuration information forthe computing device.

Another embodiment of the present invention provides a system thatprepares a computing device to enter a hibernation mode while thecomputing device is entering a sleep mode. During operation, this systemcauses the computing device to enter the sleep mode, wherein power tothe computing device is reduced, but power is maintained to volatilememory in the computing device. While computing device is entering sleepmode, the system creates a hibernation image for the device, and storesthe hibernation image in non-volatile storage. At a later time, thesystem causes the device to enter the hibernation mode, wherein theactive state of the computing device is preserved in non-volatilestorage while power to volatile storage is turned off. By creating thehibernation image while the computing device is entering the sleep mode,the system can subsequently enter the hibernation mode from the sleepmode without having to generate the hibernation image.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a computing device in accordance with an embodimentof the present invention.

FIG. 2 illustrates items stored in non-volatile random-access memory(NVRAM) in accordance with an embodiment of the present invention.

FIG. 3 illustrates the structure of a hibernation image in accordancewith an embodiment of the present invention.

FIG. 4 presents a flow chart illustrating the process of generating ahibernation image while entering sleep mode in accordance with anembodiment of the present invention.

FIG. 5 presents a flow chart illustrating the process of reanimating acomputing device from a hibernation image in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the invention, and is provided in the context ofa particular application and its requirements. Various modifications tothe disclosed embodiments will be readily apparent to those skilled inthe art, and the general principles defined herein may be applied toother embodiments and applications without departing from the spirit andscope of the present invention. Thus, the present invention is notlimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles and features disclosed herein.

The data structures and code described in this detailed description aretypically stored on a computer-readable storage medium, which may be anydevice or medium that can store code and/or data for use by a computersystem. This includes, but is not limited to, magnetic and opticalstorage devices, such as disk drives, magnetic tape, CDs (compact discs)and DVDs (digital versatile discs or digital video discs).

Computing Device

FIG. 1 illustrates a computing device 100 in accordance with anembodiment of the present invention. Computing device 100 can generallyinclude any type of computing device or system, including, but notlimited to, a computing device based on a microprocessor, a mainframecomputer, a digital signal processor, a portable computing device, apersonal organizer, a device controller, and a computational enginewithin an appliance.

Computing device 100 receives power from a battery 122, which can becoupled (through a transformer) to a source of alternating current (AC)power.

Computing device 100 includes a number of devices 110, such as a display112 and a keyboard 114, as well as a hard drive 116. Note that ahibernation image 117 can be stored on hard drive 116 as is described inmore detail below.

In additional to these devices 110, computing device 100 includes arandom-access memory (RAM) 120, as well as a non-volatile random accessmemory (NVRAM) 118.

Computing device 100 also includes an operating system 108, whichsupports the execution of a number of processes 102. Operating system108 also maintains memory management structures 104, such as pagetables, and additionally provides drivers for devices 106.

Note that although the present invention is described in the context ofthe computing device 100 illustrated in FIG. 1, the present inventioncan generally operate on any type of computing device that can support ahibernation mode. Hence, the present invention is not limited to thespecific computing device 100 illustrated in FIG. 1.

Items in NVRAM

FIG. 2 illustrates items stored in non-volatile random-access memory(NVRAM) 118 in accordance with an embodiment of the present invention.NVRAM 118 is ideally tamper-proof so that the contents of NVRAM 118 willdisappear if NVRAM 118 is removed from computing device 110.

As is illustrated in FIG. 2, NVRAM 118 stores a number of items,including: decryption key 202, booter checksum 204, hibernation flag206, image block number 208, and system configuration information 210.These items are used to support device hibernation as is described inmore detail below with reference to FIGS. 4-5.

Hibernation Image

FIG. 3 illustrates the structure of hibernation image 117 (from FIG. 1)in accordance with an embodiment of the present invention. Hibernationimage 117 includes reanimation code 302, which when executed bycomputing device 100 performs the operations required to complete thereanimation process. (Note that reanimation code can itself becompressed if the system booter supports decompression operations.)

Hibernation image 117 also contains “user pages” 304, which containstate information for the computing device and are compressed to savespace.

Hibernation image 117 additionally contains “wired pages” which are bothencrypted and compressed. These wired pages can contain sensitiveinformation, such as passwords, which need to be protected by storingthem in encrypted form in the hibernation image 117.

In one embodiment of the present invention, hibernation image 117 isreferenced only by block number. To facilitate this block-basedreferencing, hibernation image 117 contains within itself a linked listof blocks in the image. This block-based referencing enables the booterto read the image from within a block device without having anyknowledge of the file system format of the block device.

Process of Generating a Hibernation Image

FIG. 4 presents a flow chart illustrating the process of generating ahibernation image while entering sleep mode in accordance with anembodiment of the present invention. The process starts when the systemdecides to sleep (step 402). This can occur automatically, for exampleif the system is in idle or is low on power. It can also be initiated byan explicit command from a user.

In order to enter sleep mode, the system first determines whether thesystem is capable of hibernating (step 404). This can involve looking atpreset system configuration parameters. If the system is not capable ofhibernating, the system defaults to the normal sleep path, whichinvolves proceeding directly to step 412.

On the other hand, if the system is capable of hibernating, the systemperforms a number of operations in preparation for hibernation. Inparticular, the system reserves space on disk for the hibernation image(step 406). It can also evict pages for idle processes from memory (step408). This reduces the number of pages that need to be stored in thehibernation image. The system also sets a hibernation flag (step 410).This hibernation flag indicates that a hibernation image has beencreated so that when the system subsequently boots up, the system willreanimate itself from the hibernation image, instead of performing anormal boot up operation.

The system next enters the normal sleep path to perform a number ofoperations. In particular, the system notifies processes that have askedto be informed that the system is entering a sleep mode (step 412). Thesystem also notifies the operating system kernel that the system isentering sleep mode (step 414). The system can also notify variousdrivers that the system is entering sleep mode (step 416). Note that ifthe system is capable of hibernation, the disk driver does not spin thedisk down, but instead keeps the disk spinning to prepare for asubsequent hibernation image write operation.

The system next enters a “hibernation-polled mode” in which the systemprepares for hibernation. This involves examining memory managementstructures (step 418) and marking pages in memory as either having to bewritten to disk or not having to be written to disk. Note that pagesthat are already available on disk, such as pages containing applicationcode or pages that can be reconstructed from other information on disk,are marked as not having to be written to disk. Whereas, other pagescontaining modified data are marked as having to be written to disk.

Next, the system compresses and writes user pages to disk (step 420).The system also encrypts and writes “wired pages” to disk (step 422).Recall that these wired pages may contain sensitive information, such aspasswords, so it is desirable to encrypt them before they are stored ondisk. The system also stores a corresponding decryption key, which canbe used to decrypt to the encrypted pages, to NVRAM.

Finally, the system generates and writes reanimation code to disk (step424). This reanimation code can be subsequently used to reanimate thehibernation image.

Next, the system can optionally set a timer which indicates the timewhen the system will subsequently enter hibernation mode (step 426).Finally, the system enters sleep mode (step 430), wherein power to thesystem is reduced, but power is maintained to volatile memory. If thesystem remains in sleep mode until the timer expires, the system willenter hibernation mode, wherein power to volatile storage is turned off.Note that by creating the hibernation image while the computing deviceis entering the sleep mode, the system can subsequently enter thehibernation mode from the sleep mode without having to generate thehibernation image. This is a significant advantage because when thesystem ultimately decides to hibernate there may be very little batterypower left to generate a hibernation image. The hibernation operationsalso involve significant disk activity, which may be surprising to theuser if this disk activity occurs at a later time. Furthermore, whenwaking up to create the hibernation image, the system is not guaranteedto be in a safe operating environment. It could be in the overhead binon an airline flight, in the trunk of an automobile on a bumpy road, orcould be subjected to even worse adverse conditions.

Process of Reanimating a Computing Device from a Hibernation Image

FIG. 5 presents a flow chart illustrating the process of reanimating acomputing device from a hibernation image in accordance with anembodiment of the present invention. This process starts during a normalboot up operation of computing device 100, which involves executing codefrom a system Boot Read-Only Memory (ROM) (not illustrated). First, thesystem performs a minimal initialization of the hardware (step 502).Next, the system checks if the hibernation flag 206 is set (step 506).If not, the system defaults to performing a normal boot operation (step507).

On the other hand, if hibernation flag 106 is set, the system reads thepreviously stored decryption key 202 and booter checksum 204 from NVRAM118 (step 508). The system then erases decryption key 202 and booterchecksum 204 from NVRAM 118 (step 510). The system also compares thesystem configuration against the previously stored system configurationinformation 210 to verify that the system configuration has not changedsince hibernation image 177 was created (step 512). If the configurationhas changed, the system can perform a remedial action, such asdefaulting to a normal boot operation. On the other hand, if the systemconfiguration has not changed, the system disables “snag keys,” whichare used to select different boot modes (step 514).

The booter then commences executing a shortened boot path. During thisshortened boot path, the system determines if the booter checksum 204matches the booter checksum of the booter that is presently performingthe boot up process (step 516). If not, the system defaults to thenormal boot process (step 507). Otherwise, if booter checksum 204matches the current booter's checksum, the system allows the booter toobtain the decryption key 202 (step 518).

Next, the system retrieves hibernation image 117 from the locationsspecified by the previously-stored image block number 208 (step 524).The system then restores the reanimation code 302 from hibernation image117 (step 526), and begins executing reanimation code 302 (step 528).

Reanimation code 3027 effectively contains a “mini-kernel” whichrestores the rest of the state of computing device 100 from hibernationimage 117 (step 530). More specifically, this involves reading anddecompressing user pages 304 as well as reading, decompressing anddecrypting wired pages 306. During this process, the reading operationscan take place in parallel with the decompression operations to improveperformance. This assumes that multiple buffers exist so that data canbe read to a first buffer while data is being decompressed from a secondbuffer. The system also sets a reanimation flag so thathibernation-aware drivers can determine that this is not a normal wakeoperation (step 532).

Finally, after hibernation image 117 has been restored, the systemperforms a normal wake-from-sleep operation (step 534). During thisprocess, the system can lazily evict clean pages that had valid data inthem at image-creation time, but were not saved in order to reduce theimage-writing time. Note that these clean pages are evicted only ifpower to memory was lost prior to the image-restoration process.

The foregoing descriptions of embodiments of the present invention havebeen presented only for purposes of illustration and description. Theyare not intended to be exhaustive or to limit the present invention tothe forms disclosed. Accordingly, many modifications and variations willbe apparent to practitioners skilled in the art. Additionally, the abovedisclosure is not intended to limit the present invention. The scope ofthe present invention is defined by the appended claims.

1. A method for reanimating a computing device from a hibernation image,comprising: restoring reanimation code from the hibernation image;executing the reanimation code, wherein executing the reanimation codecauses the computing device to restore the rest of the hibernation imageby: reading compressed data containing the rest of the hibernationimage; decompressing the compressed data using computational circuitrywithin the computing device, wherein the decompression operations areoverlapped with the reading operations to improve performance during thereanimation process; and setting a reanimation flag so thathibernation-aware drivers can determine that a following wake-from-sleepoperation is not a normal wake-from-sleep operation, but is instead partof a reanimation operation; and performing a wake-from-sleep operationto reanimate the computing device from the decompressed hibernationimage.
 2. The method of claim 1, wherein restoring the rest of thehibernation image additionally involves: reading a decryption key fromnon-volatile random access memory; and using the decryption key todecrypt portions of the compressed data containing the rest of thehibernation image which were encrypted prior to storage in non-volatilememory.
 3. The method of claim 1, wherein prior to restoring thereanimation code, the method further comprises: comparing a storedbooter checksum, which was stored while generating the hibernationimage, against a current booter checksum for a booter which is currentlyrestoring the animation code; and if the stored booter checksum does notmatch the current booter checksum, discontinuing the reanimationprocess.
 4. The method of claim 1, wherein prior to restoring thereanimation code, the method further comprises: examining stored deviceconfiguration information, which was stored when the hibernation imagewas generated, to determine whether the configuration of the computingdevice has changed since the hibernation image was generated; and if theconfiguration of the computing device has changed, discontinuing thereanimation process.
 5. A computing device including a mechanism forreanimating the computing device from a hibernation image, comprising: aprocessor; a memory; a device-initialization mechanism, which isconfigured to, restore reanimation code from the hibernation image;execute the reanimation code, wherein executing the reanimation codecauses the computing device to: read compressed data containing the restof the hibernation image; decompress the compressed data usingcomputational circuitry within the computing device, wherein thedecompression operations are overlapped with the reading operations toimprove performance during the reanimation process; and set areanimation flag so that hibernation-aware drivers can determine that afollowing wake-from-sleep operation is not a normal wake-from-sleepoperation, but is instead part of a reanimation operation; and perform awake-from-sleep operation to reanimate the computing device from thedecompressed hibernation image.
 6. A computer-readable storage mediumstoring instructions that when executed by a computer cause the computerto perform a method for reanimating a computing device from ahibernation image, the method comprising: restoring reanimation codefrom the hibernation image; and executing the reanimation code, whereinexecuting the reanimation code causes the computing device to restorethe rest of the hibernation image by: reading compressed data containingthe rest of the hibernation image; decompressing the compressed datausing computational circuitry within the computing device, wherein thedecompression operations are overlapped with the reading operations toimprove performance during the reanimation process; and setting areanimation flag so that hibernation-aware drivers can determine that afollowing wake-from-sleep operation is not a normal wake-from-sleepoperation, but is instead part of a reanimation operation; andperforming a wake-from-sleep operation to reanimate the computing devicefrom the decompressed hibernation image.
 7. The computer-readablestorage medium of claim 6, wherein restoring the rest of the hibernationimage additionally involves: reading a decryption key from non-volatilerandom access memory; and using the decryption key to decrypt portionsof the compressed data containing the rest of the hibernation imagewhich were encrypted prior to storage in non-volatile memory.
 8. Thecomputer-readable storage medium of claim 6, wherein prior to restoringthe reanimation code, the method further comprises: comparing a storedbooter checksum, which was stored while generating the hibernationimage, against a current booter checksum for a booter which is currentlyrestoring the animation code; and if the stored booter checksum does notmatch the current booter checksum, discontinuing the reanimationprocess.
 9. The computer-readable storage medium of claim 6, whereinprior to restoring the reanimation code, the method further comprises:examining stored device configuration information, which was stored whenthe hibernation image was generated, to determine whether theconfiguration of the computing device has changed since the hibernationimage was generated; and if the configuration of the computing devicehas changed, discontinuing the reanimation process.